Fix radio timeout #244
Merged
Fix radio timeout #244
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
We can nest it as a single pattern.
jonathanpallant
force-pushed
the
radio-fixes
branch
from
ba072ba to
bb98043
Compare
Deploying ferrous-systems-rust-exercises with
|
| Latest commit: |
6804d52
|
| Status: | ⚡️ Build in progress... |
jonathanpallant
force-pushed
the
radio-fixes
branch
from
c405f8a to
bb98043
Compare
mhatzl
approved these changes
Dec 9, 2025
mhatzl
left a comment
mhatzl
left a comment
There was a problem hiding this comment.
can confirm.
running cargo run --bin radio-puzzle-solution without a dongle attached hangs the application.
with this PR, I get
00:00:00.210815 [ERROR] no response or response packet was corrupted (radio_puzzle_solution src/bin/radio-puzzle-solution.rs:42)
`dk::exit()` called; exiting ...
Firmware exited successfully
Member
Author
|
Why is cloudflare sad?
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fixes #243
It was a simple typo - the code was reading the task register instead of firing the task (which you do by writing to it).
cc @robamu